Q: My NeXTstation won't boot from the network. I think I set everything up correctly: the ethernet address, kernel, and boot parameters are correct in NetManager, I've built a client partition on the server and ensured it and the root filesystem are exported correctly. If I boot the machine from its hard disk, it sees the network and can mount everything from the server. What's wrong?\
\
A: Most likely, you have a pre-release NeXTstation, or a NeXTstation with a pre-release PROM. Check the version of the PROM (in the NeXT ROM Monitor window's title bar); if it is V55 or lower, the PROM is requesting jksboot.\
\
Alternatively, you can examine the request received by
\b bootpd
\b0 , the boot protocol daemon. (This technique is useful if you suspect something else strange is happening during the NetBoot sequence.)\
\
\pard\tx900\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\fi-280\li900 • Log in as
\pard\tx900\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\f0\fs28\fi-280\li900 Keep the Terminal window open; that's where you'll see the syslog messages for
\b bootpd
\b0 .\
\
\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600 Now, reboot the client machine. You'll see messages like this in your Terminal window:\
\
\pard\tx260\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\f3\fs24\li840\fc0 Nov 27 11:41:33 server1 syslog: request from client for 'boot'\
Nov 27 11:41:33 server1 syslog: replyfile /private/tftpboot/boot\